Terraform Associate (004) Practice Exam — Terraform Associate (004)

Option Analysis: A. This option is correct because a core benefit and standard practice of Infrastructure as Code is storing declarative configuration files alongside application code in a version control system like Git to enable collaborative change tracking, auditability, and consistent infrastructure deployment. B. This option is incorrect because storing IaC alongside application code in version control is a widely adopted standard practice that aligns with DevOps and IaC core principles. Key Concept: A core principle of Infrastructure as Code is that configuration files are treated like any other source code, enabling their storage in version control systems alongside application code to leverage versioning, change review, and automation workflows. References: What is Infrastructure as Code?, https://developer.hashicorp.com/terraform/tutorials/aws-get-started/infrastructure-as-code Infrastructure as Code Overview, https://www.redhat.com/en/topics/automation/what-is-infrastructure-as-code-iac

Option Analysis: A. Option A is incorrect because storing unencrypted secret data in version control exposes sensitive credentials to anyone with access to the repository, and secrets cannot be fully removed from git history once committed, violating security best practices. B. Option B is correct because best practices require Terraform secret data to be managed via dedicated secret tools or encrypted state instead of plaintext in version control. Key Concept: Terraform security best practices mandate that sensitive secret data must never be stored as plaintext in version control alongside configuration, to prevent unauthorized exposure of credentials. References: Sensitive Data in Terraform, https://developer.hashicorp.com/terraform/tutorials/configuration-language/sensitive-variables HashiCorp Recommended Practices: Protecting Secrets

Option Analysis: A. This option is correct because infrastructure as code stores infrastructure definitions as plain editable text files, which can be version controlled with tools like Git, reused across environments, and shared with teams, capabilities that are not possible with one-off manual GUI-based provisioning. B. This option is incorrect because GUI-based provisioning also requires entering credentials, and does not inherently secure credentials any worse than IaC, so this is not a unique advantage. C. This option is incorrect because IaC does not inherently lower the cost of the cloud resources you provision, so this is not a valid unique advantage. D. This option is incorrect because neither IaC nor GUI provisioning inherently prevent manual modifications to deployed resources, unless additional guardrails are implemented separately, so this is not a unique advantage. Key Concept: Infrastructure as Code (IaC) treats infrastructure definitions as editable text artifacts, enabling core DevOps practices like version control, modular reuse, and team sharing that are not available with manual GUI-based provisioning. References: What is Infrastructure as Code?, HashiCorp, https://developer.hashicorp.com/terraform/tutorials/aws-get-started/infrastructure-as-code Terraform Associate Certification Study Guide, HashiCorp

Option Analysis: A. This option is incorrect because automatic infrastructure upgrades are not an inherent advantage of immutable infrastructure, and this functionality can exist in mutable infrastructure patterns as well. B. This option is incorrect because in-place upgrades are the core characteristic of mutable infrastructure, not immutable infrastructure. C. This option is incorrect because immutable infrastructure deployments are not inherently quicker than in-place mutable upgrades, as they require provisioning entirely new infrastructure instead of modifying existing resources. D. This option is correct because immutable infrastructure upgrades replace existing instances with new pre-tested infrastructure instead of modifying in-place, eliminating configuration drift and unexpected side effects that add complexity to upgrade processes. Key Concept: Immutable infrastructure is a pattern where infrastructure is replaced entirely rather than modified after deployment, which reduces the risk of configuration inconsistency and simplifies the upgrade process when compared to mutable in-place upgrades. References: What is Immutable Infrastructure?, HashiCorp, Immutable Infrastructure, Terraform Official Documentation

Option Analysis: A. Option A is incorrect because defining a pipeline to test and deliver software is the purpose of CI/CD tooling, not Infrastructure as Code. B. Option B is incorrect because while IaC can reduce long-term costs, cost reduction is not its primary core purpose. C. Option C is correct because the fundamental primary purpose of Infrastructure as Code is to programmatically define, create, and manage infrastructure resources instead of using manual physical or GUI-based configuration processes. D. Option D is incorrect because Infrastructure as Code is not primarily designed to create a vendor-agnostic API, though some IaC tools can work across multiple vendors. Key Concept: Infrastructure as Code is the core foundational practice Terraform implements, with the primary goal of programmatically version-controlled management of infrastructure creation and configuration. References: What is Infrastructure as Code?, HashiCorp, https://developer.hashicorp.com/terraform/tutorials/aws-get-started/infrastructure-as-code Infrastructure as Code Overview, Terraform Official Documentation